Skip to content

Comments

[MrBot] Add coding guidelines learnings from feature flags PR #14521373#324

Open
dcristoloveanu wants to merge 1 commit intomasterfrom
dcristo/learnings-from-feature-flags-pr
Open

[MrBot] Add coding guidelines learnings from feature flags PR #14521373#324
dcristoloveanu wants to merge 1 commit intomasterfrom
dcristo/learnings-from-feature-flags-pr

Conversation

@dcristoloveanu
Copy link
Member

Summary

Adds 3 learnings extracted from PR review comments on Azure-MessagingStore PR #14521373 (feature flags implementation).

Learnings Added

1. .CallCannotFail() Modifier Rules

Use .CallCannotFail() on expected calls ONLY in umock negative tests to exclude specific calls from failure injection. Do NOT use it in positive/happy path tests where it has no effect.

2. SRS Requirements Must Be Individually Taggable

Each SRS requirement should describe a single testable behavior. Combined specs (e.g., 'returns A or B') should be split into separate specs for independent test tagging.

3. Exposed API Section Must Mirror the Header

The Exposed API section in requirements docs must contain all public enums, typedefs, and function declarations exactly as they appear in the public header file.

Session

Copilot session: ce97c609-5e29-446e-9557-f92b318c2e8e

@dcristoloveanu dcristoloveanu force-pushed the dcristo/learnings-from-feature-flags-pr branch from cdc1caf to 2eadba8 Compare February 19, 2026 04:14
@dcristoloveanu
Copy link
Member Author

/azp run Azure-C-Build-Tools-Gate

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Added 3 learnings extracted from PR review comments:
1. .CallCannotFail() modifier rules - only use in negative tests (placed in Negative Testing section)
2. SRS requirements must be individually taggable per test
3. Exposed API section in requirements must mirror the header

Also removed duplicate Struct Arguments Require IGNORED_STRUCT_ARG section (already present from master).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dcristoloveanu dcristoloveanu force-pushed the dcristo/learnings-from-feature-flags-pr branch from 2eadba8 to 7d14cbc Compare February 19, 2026 04:25
@dcristoloveanu
Copy link
Member Author

/azp run Azure-C-Build-Tools-Gate

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@BertKleewein BertKleewein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants